@William-Kansepa This issue should be fixed in build 1.1.062